Skip to content

ci: Fix integration tests failing on fork PRs#655

Merged
vdusek merged 2 commits intomasterfrom
ci/fix-integration-tests-fork-prs
Mar 6, 2026
Merged

ci: Fix integration tests failing on fork PRs#655
vdusek merged 2 commits intomasterfrom
ci/fix-integration-tests-fork-prs

Conversation

@vdusek
Copy link
Contributor

@vdusek vdusek commented Mar 2, 2026

Summary

  • Inline integration tests in the CI workflow instead of calling the reusable workflow to avoid GitHub's compile-time secret validation for nested reusable workflows, which fails on fork PRs where repo secrets are not available
  • Add workflow_dispatch to the integration tests condition
  • Remove unnecessary secrets: inherit from unit tests

This follows the same pattern as in the Python SDK: https://github.com/apify/apify-sdk-python/blob/master/.github/workflows/_tests.yaml

Test plan

  • Verify the workflow syntax is valid
  • Integration tests should run on PRs from the apify org, pushes to master, and manual triggers
  • Integration tests should be skipped on fork PRs

🤖 Generated with Claude Code

@vdusek vdusek added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Mar 2, 2026
@vdusek vdusek self-assigned this Mar 2, 2026
@vdusek vdusek added adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team. labels Mar 2, 2026
@github-actions github-actions bot added this to the 135th sprint - Tooling team milestone Mar 2, 2026
@vdusek vdusek marked this pull request as draft March 2, 2026 13:54
@codecov
Copy link

codecov bot commented Mar 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.41%. Comparing base (21f2665) to head (3a6d39c).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #655      +/-   ##
==========================================
- Coverage   96.45%   94.41%   -2.04%     
==========================================
  Files          45       45              
  Lines        4318     4318              
==========================================
- Hits         4165     4077      -88     
- Misses        153      241      +88     
Flag Coverage Δ
integration 94.41% <ø> (-0.05%) ⬇️
unit ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

The integration tests were failing on fork PRs with "Secret
APIFY_TEST_USER_PYTHON_SDK_API_TOKEN is required, but not provided"
because GitHub validates required secrets of nested reusable workflows
at compile time, before evaluating job-level `if` conditions.

Inline the integration test steps directly in _tests.yaml instead of
calling the external reusable workflow. Regular job steps that reference
secrets just get empty strings for fork PRs (no compile-time validation),
and the `if` condition properly skips the job.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vdusek vdusek force-pushed the ci/fix-integration-tests-fork-prs branch from 957ac11 to cec0cc5 Compare March 6, 2026 10:00
@vdusek vdusek requested a review from Pijukatel March 6, 2026 10:25
@vdusek vdusek marked this pull request as ready for review March 6, 2026 10:27
@vdusek vdusek merged commit b73ba94 into master Mar 6, 2026
26 checks passed
@vdusek vdusek deleted the ci/fix-integration-tests-fork-prs branch March 6, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants